3.7.5 -
3.7.5 |
Device.lastCalibrationTime :: TS (0..1)
|
Attribute
description:
The date/time of the last calibration of
the device.
Ratonale: Devices are required to be recalibrated
at specific intervals to ensure they are performing within specifications. The
accepted interval between calibrations varies with protocols. Thus for results
to be valid, the precise time/date of last calibration is a critical component.
OpenIssue: Is this linked somehow with the
'maintainer'?
OpenIssue: Given the definition of the class, this
attribute would be moved up to ManufacturedMaterial.
Recommendation: drop open
issues
3.10.2 |
Diet.carbohydrateQuantity :: PQ (0..1)
|
Attribute
description:
The supplied amount of carbohydrates (g)
per day.
Discussion: For diabetes diet one typically
restricts the amount of metabolized carbohydrates to a certain amount per day
(e.g., 240 g/d). This restriction can be communicated in the carbohydrateQuantity.
OpenIssue: Unclear whether the same should not be
expressed as associated observations in goal mood (observation.typeCode = carbohydrate intake.)
Recommendation: drop open
issue
3.12.13 |
Entity.importanceStatusText :: ED (0..1)
|
Attribute
description:
A textual or multimedia depiction of the
relative importance the Entity has to other
Entities.
OpenIssue: There is a problem with this attribute.
Shouldn't it be coded? Does it belong here at all?
Recommendation: drop the
attribute, it could be accommodated when needed as on
observation against the entity.
3.22.1 |
Material.formCode
:: CE (0..1)
|
Vocabulary domain:
MaterialForm (CWE)
Attribute
description:
A value representing the state (solid,
liquid, gas) and nature of the material.
Examples: For therapeutic substances, the dose
form, such as tablet, ointment, gel, etc.
OpenIssue: Vocabulary domain should include, but is
broader than, the DoseForm domain.
Recommendation: drop the open issues since
DoseForm is no longer the name of the Domain for this
attribute.
3.27 |
Class:
Patient (in Roles)
|
·
Attributes of
Patient:
|
|
|
|
·
Patient is a
specialization of: Role
A Role of a LivingSubject (player) as a recipient of health care
services from a healthcare provider (scoper).
OpenIssue: This is really a kind of Customer role.
Recommendation:
drop the open issue
3.29.2 |
Person.maritalStatusCode :: CE (0..1)
|
Vocabulary domain:
MaritalStatus (CWE)
Attribute
description:
A value representing the domestic
partnership status of a person,
Examples: Married, separated, divorced, widowed,
common-law marriage.
Rationale: This information is reported on UB FL 16
OpenIssue: It is not clear what the temporal values
are and whether or not items such as divorced/married are mutually exclusive.
OpenIssue: Probably competing existing code schemes.
Recommendation:
drop the open issue, because the issue is against the value set which is not
being balloted.
3.29.3 |
Person.educationLevelCode :: CE (0..1)
|
Vocabulary domain:
EducationLevel (CWE)
Attribute
description:
The level of education a person
achieved.
OpenIssue: Need example values.
Recommendation: refer to PA to add
examples
3.29.4 |
Person.disabilityCode :: CE (0..1)
|
Vocabulary domain:
PersonDisabilityType (CWE)
Attribute
description:
A value identifying a person's
disability.
Examples: vision impaired, hearing impaired.
OpenIssue: Need example values.
Recommendation:
remove OpenIssue
OpenIssue: Shouldn't this be SET<CE>
Recommendation:
accept and adopt the SET<CE> and change cardinality to 0..*
3.29.6 |
Person.religiousAffiliationCode
:: CE (0..1)
|
Vocabulary domain:
ReligiousAffiliation (CWE)
Attribute
description:
A value representing the religious
preference for a person
OpenIssue: Need example values.
Recommendation:
refer to PA for examples
3.30.5 |
Place.gpsText
:: ST (0..1)
|
Attribute
description:
The global positioning system coordinates
of a place.
Discussion: The global positioning system values for
this attribute should conform with the USGS Spatial
Data Tranmission Standards. Among other things this
includes the nature of the latitude and longitude readings, the offset error,
the projection.
Rationale: In some field conditions, there will be
no physical address to identify a place of interest. As all locations on the
surface of the earth have unique geografic coordinates,
the GPS values allow for precise locational
information to be capture and transmitted.
OpenIssue: This is really the GPS coordinates, and
needs a different data type to capture the integers. Also, it needs a
description.
Recommendation:
1. change the data type to LIST<INT>
Recommendation:
2. drop open issue: description is present
3.38 |
Class:
WorkingList (in Acts)
|
·
Attributes of WorkingList:
|
|
|
|
·
WorkingList is a
specialization of: Act
A dynamic list of individual instances of
Act which reflect the needs of an individual worker, team of workers, or an
organization to view groups of Acts for clinical or administrative
reasons.
Discussion: The grouped Acts are related to the
WorkingList via an ActRelationship of type 'COMP' (component).
Examples:problem lists, goal lists, allergy lists, to-do
lists, etc.
OpenIssue: The name is too generic. This needs to
be harmonized with Scheduling.
Recommendation:
drop the open issue